Adding a doc for server release process #538
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
venky-wandb
reviewed
Dec 27, 2023
| For both cases above, such updates are applied to the whole **Dedicated Cloud** fleet in batches, and we can not exclude a particular instance from the process. Customers with **Self-managed** instances are responsible to manage such updates on their own schedule. Refer to [release support and end of life](#release-support-and-end-of-life). | ||
|
|
||
| ## Release support and end of life | ||
| We officially support server releases from last six months. This should not affect the **Dedicated Cloud** instances as we update those as part of the release process. But customers with **Self-managed** instances should ensure that they're updating their deployment(s) with the latest release when possible. Staying on a version older than six months would mean that they have limited to no means of support. |
There was a problem hiding this comment.
Staying on a version older than six months would mean that they have limited to no means of support.
We may benefit from adding something similar to this into the actual contract itself.
There was a problem hiding this comment.
Yeah, that would be a separate thing later. For now I want to get it into the docs.
venky-wandb
approved these changes
Dec 27, 2023
cvphelps
approved these changes
Dec 28, 2023
ngrayluna
approved these changes
Dec 28, 2023
|
Thanks Noah! @abhinavg6 this will go out tomorrow in the docs deployment! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add a new doc for server release process, covering the frequency, release notes, downtime aspects, and end of life policy.
Ticket
NA
Checklist
Check if your PR fulfills the following requirements. Put an
Xin the boxes that apply.yarn start. My changes did not break the local preview.yarn docusaurus build) was run locally and successfully without errors or warnings. - still getting unrelated TypeError: Invalid URL errors.maininto my feature branch before submitting this PR.